Skip to content

Updating benchmark sections because of the new round 23 of techempower benchmarks #640

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Updating benchmark sections because of the new round 23 of techempower benchmarks #640

wants to merge 2 commits into from

Conversation

RedEagle-dh
Copy link

@RedEagle-dh RedEagle-dh commented Sep 28, 2025 •
edited by coderabbitai bot
Loading

Summary

This PR updates the benchmark section to reflect the latest results from
TechEmpower Benchmark Round 23 (2025-02-24, PlainText).

Changes

  • Updated the correct req/s values in benchmark section of the landing page, express to elysia and fastify to elysia pages.
  • Adjusted expand values to correctly represent relative performance
    (baseline: Elysia = 72).
  • Updated request/second values for:
    • Elysia
    • Gin
    • Fastify
    • Spring
    • Express
    • Nest

Context

The previous expand values did not reflect the actual proportional differences
between frameworks. With Round 23 results now published, the numbers have been
recalculated to be consistent and visually accurate.

Reference

TechEmpower Benchmarks – Round 23

Summary by CodeRabbit

  • Documentation
    • Updated benchmark metrics to TechEmpower Round 23 (2025-02-24) across docs components.
    • Revised reqs/s values and progress bar widths for Elysia, Fastify, Express, Nest, Gin, and Spring/Java.
    • Adjusted comparative multipliers (e.g., 21x→93x, 6x→22x) and reordered framework listings to reflect latest results.
    • Updated benchmark links to the data-r23 plaintext section.
    • Textual/date references refreshed; no functional changes.

@RedEagle-dh
chore(benchmarks): Updating sections benchmark (landing), `migratin…
4c26a99 
…g from express` and `migrating from fastify` with new round 23 from techempower benchmark
@RedEagle-dh
fix(benchmark): adjust expand values to reflect correct relative perc…
bc97c55 
…entages (Elysia = 72 baseline)
@coderabbitai coderabbitai
Copy link

coderabbitai bot commented Sep 28, 2025 •
edited
Loading

Walkthrough

Documentation and UI content were updated to reflect TechEmpower Benchmark Round 23 (2025-02-24). Three Vue docs components had displayed metrics, labels, widths, and links refreshed. One markdown doc updated its reference note. No logic, control flow, or exported entities changed.

Changes

Cohort / File(s) Summary
Docs reference update
docs/at-glance.md		 Updated benchmark reference note from Round 22 to Round 23; content-only change.
Benchmark UI components
docs/components/fern/benchmark.vue, docs/components/fern/benchmark-fastify.vue, docs/components/fern/benchmark-express.vue		 Refreshed displayed metrics (reqs/s), progress widths, label ordering/mapping, and benchmark link params from section=data-r22 to section=data-r23; updated round/date text to 2025-02-24. No control-flow or logic changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my ears at Round Twenty-Three,
New numbers hop across the UI with glee.
Bars stretch, links leap, dates realign—
No codepaths burrow, all looks fine.
Thump-thump! Benchmarks fresh as dew,
A happy hare commits something new. 🥕

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title succinctly conveys that the benchmark sections are being updated to reflect the new TechEmpower Round 23 results and is fully aligned with the primary changes made in the pull request.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8e16219 and bc97c55.

📒 Files selected for processing (4)
  • docs/at-glance.md (1 hunks)
  • docs/components/fern/benchmark-express.vue (1 hunks)
  • docs/components/fern/benchmark-fastify.vue (1 hunks)
  • docs/components/fern/benchmark.vue (3 hunks)
🔇 Additional comments (4)
docs/at-glance.md (1)

323-324: Round 23 reference looks good

Pointing the note to Round 23 keeps the doc aligned with the latest published TechEmpower run and its updated hardware context. (techempower.com)

docs/components/fern/benchmark-express.vue (1)

16-34: Express benchmark card updated coherently

The new req/s values, width ratio, and Round 23 link all line up with the latest TechEmpower run—nice job keeping this card in sync. (techempower.com)

docs/components/fern/benchmark-fastify.vue (1)

16-34: Fastify benchmark card stays consistent

The refreshed numbers, scaled width, and updated Round 23 attribution keep this card in lockstep with the current TechEmpower data. (techempower.com)

docs/components/fern/benchmark.vue (1)

29-107: Main benchmark panel refresh is consistent

Updating the headline multipliers, expand factors, and req/s values together keeps the entire visualization internally consistent and aligned with the Round 23 dataset. Thanks for tackling all the dependent bits in one pass. (techempower.com)

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@RedEagle-dh